home *** CD-ROM | disk | FTP | other *** search
- Path: solon.com!not-for-mail
- From: schwarz@mips.complang.tuwien.ac.at (Konrad Schwarz)
- Newsgroups: comp.lang.c,comp.lang.c.moderated,comp.lang.c++,comp.lang.misc
- Subject: Re: Need C or C++ Embedded Interpreter
- Date: 16 Apr 1996 20:44:06 -0500
- Organization: TU Wien
- Sender: clc@solutions.solon.com
- Approved: clc@solutions.solon.com
- Message-ID: <4l1id6$pva@solutions.solon.com>
- References: <4ku413$57i@solutions.solon.com>
- NNTP-Posting-Host: solutions.solon.com
-
- A difficulty I see with an extendible printf is devising a mechanism
- so that unrelated modules can cooperate on extensions. Suppose library
- A and B both decide to assign format letter b, and J. Random Luser decides
- to use A and B in the same program. When the second library to assign the
- format notices that b has already been assigned, it has no choice but
- to search for a different, unassigned letter and then rewrite all its
- format strings---ruling out the use of format extensions in libraries
- for all practical purposes. I don't think that any of the current
- (ANSI) library functions have this problem, since they tend give you
- something, i.e., a FILE * or a file descriptor, instead of allowing you
- to request a certain object.
-
- Konrad Schwarz
-